Visible Assets Dot-Tag Visibility Network Architecture

ABSTRACT

The system employs full transceivers, each having peer-to-peer, client/server, and IP networking capabilities, and covering open-area ranges of up to 100 feet. The system uses Low Frequency for data communications so it can achieve both low cost (less costly than many RF-ID tags) and long battery life (10-15 years). Additionally, since these tags have batteries, static RAM maybe be added at very low cost, as well as sensors, LED&#39;s displays etc. The system also employs a sidewinder that communicates to said tag regularly, said sidewinder keeps the IP address of said tag. The system also employs an embedded VPN. The VPN includes a suite of diagnostic tools that run on a laptop. The diagnostic tools talk direct to the sidewinder, the tools read and program said tag providing the tools have correct IP address of the tag. The system also includes a visibility data server that communicates to the sidewinder by the VPN. The data server includes a virtual tag data base, said virtual tag data base updated by the sidewinder. The web enabled reports and control are managed by two “plugs”. The SQL plug supports data requests, and the Air Traffic Control (ATC) plug provides control (LED&#39;s, read rates). The system also employs a user web based ERP to create a real-time visibility reports and a user event export tools to create reports that fit a specific event.

This application claims priority from U.S. application No. 60/805,020filed Jun. 16, 2006, which application is incorporated herein byreference for all purposes.

BACKGROUND

Prior-art systems use RF tags that can be subjected to anyElectromagnetic Interference (EMI) risk to hearing aid wearers,pacemakers, or IDC patients and had problems with ElectromagneticCompatibility worldwide.

Prior-art systems always had bandwidth as an issue. Prior-art systemsalso had high cost, low client count, short battery life and can onlyfunction in mild environment (away from steel and water). Manycost-sensitive, power “limited” applications exist (e.g., mostindustrial visibility networks) that may not require bandwidth, yet dorequire real-time, peer-to-peer networking with extended battery life.

The purpose for the below-described preferred embodiment to addressabove-listed problems within a long-wavelength network.

SUMMARY

The Visibility Network is designed to provide real-time web enabledasset visibility. The RuBee IV protocol was designed to work reliably ina local visibility network and provide real-time visibility for assets,people, and livestock, pedigree and provide chain of possession events.

RuBee works over a controlled-range, wide area (1′×1′ to 100′×100′) inharsh environments (that is, near metals, liquids and through earth),with an extended battery life (10-15 years), and a high safety standard.The network's design goal was to create a low cost two-way radio tagthat is safe for use in hospital patient-based settings, hospitaloperating rooms, airports and other public facilities. RuBee could notaccept any Electromagnetic Interference (EMI) risk to hearing aidwearers, pacemaker, or IDC patients and has no known or ElectromagneticCompatibility (EMC) issues worldwide. Yet, RuBee provides range and thereliability needed to produce a real-time visibility network. Everyradio tag attached to an asset appears to be a mini-web asset serverwithin the Visibility Network. The Long Wavelength ID (LWID) tag has anantenna operable at a low radio frequency not exceeding 1 megahertz Thetag also has a radiating transceiver operatively connected to saidantenna, the transceiver operates to transmit and receive data at lowradio frequency. The tag also has a programmed data processor to processdata received from the transceiver. The data processor usually is a lowcost 4-bit processor capable of encrypting and decrypting and complexfunctions associated with managing IP addresses. The tag associated witha first IP address. The tag has a volatile memory that stores said IPaddress. The transceiver emits an identification signal based upon saidIP address stored in the volatile memory. The tag also has an energysource used for activating the transceiver and the data processor. AnyRuBee IV tag if enabled properly may be searched and discovered onGoogle or the VAI “Dot-Tag” network.

The local network of tags talks to a RuBee Router (Sidewinder). TheSidewinder manages the local tag net in real time in much the same wayany WiFi router manages a TCP/IP network. The Sidewinder communicates bya VPN to a data server which manages a PostgresSQL database of virtualtags (the Dot-Tag Visibility Data Server).

Long wavelength, produces little, if any energy dissipated in the formof an electrical field (E). Long wavelength transmissions radiate energy(99.99%) in the form of a magnetic field (H). The RuBee radio tags areinductive tags and typically need a minimum signal of 0.1 milligauss toa maximum of about 300 milligauss for reliable communication. Thestrongest field near or on top of a base station antenna can be about1200 milligauss, however most standard antennas are in the 100-300milligauss range. To help provide some context for these values, theearth's magnetic field is 300-600 milligauss.

The systems are installed in several major retailers as in-storeinventory visible systems, in hospitals to provide medical devicevisibility, other healthcare applications providing real time inventoryvisibility on high valued products throughout distribution, inagricultural applications providing visibility and age verification forcattle, and in other industries providing identity systems andvisibility systems for patients, physicians, policemen, firemen,correctional officers and corporate employees.

The advantage of this system low cost to clients, low cost base stationsand routers, long battery life tags, high client/tag counts within asingle network, and work in harsh environments (near steel and water).

DESCRIPTION OF THE DRAWING

FIG. 1 shows a block diagram of a Visibility Network.

FIG. 2 shows a block diagram of a Dot-Tag Visibility Network and a UserApplication Visibility Network.

FIG. 3 shows a block diagram for the Dot-Tag Visibility Network.

FIG. 4 shows a block diagram of a Long Wavelength Tag.

FIG. 5 shows a block diagram of a diagnostic tools used in the Dot-TagVisibility Network.

FIG. 6 shows a block diagram of a Part11 Data Flow.

FIG. 7 shows another block diagram of the Part11 Data Flow.

FIG. 8 shows a block diagram of a Visibility Data Flow.

FIG. 9 shows another block diagram of the Visibility Data Flow.

FIGS. 10-13 show example of a real life application of the VisibilityNetwork.

DETAILED DESCRIPTION

FIG. 1 shows one exemplary Visibility Network 100 in accordance with oneembodiment. The Visibility Network 100 includes six layers. The firstlayer 101 is a RuBee IV Network Layer. The second layer 102 is a RuBeewireless network connection. The third layer 103 is an embedded VPNconnection between the second layer 104 and a forth layer 104. The forthlayer 104 is a data plus control that creates and preserves a data in avirtual tag data base. The fifth layer 105 is a visibility ERP and thesixth layer 106 is a Visibility Export layer.

FIG. 2 shows a block diagram 200 of the Visibility Network 100 thatincludes a Dot-Tag Visibility Network 201 and a User Visibility Network202.

FIG. 3 is a block diagram 300 that shows The Dot-Tag Visibility Network201. The Dot-tag Visibility Network 201 starts with many local RuBeeNetworks' 301. In a RuBee Network 301 each sidewinder 302 communicatesto the RuBee Tags 301 a through 301 n contained within its local netregularly. This time set by the user (each 10 minutes typical). Thesidewinder 302 keeps a table of IP addresses and subnet addresses of allactive and legible tags plus all tag data within its RuBee network. 301.If a tag 301 a has problems or is missing or has a bad CRC check it getsflagged in a trouble table. If any new tag appears within a Network itis placed in the new tag table. Each sidewinder 302 is connected to aVisibility Data Server 304 by a VPN link 303 and preserves a Virtual TagDatabase (VTDB) 305.

The VTDB 305 is shared by many Sidewinders 302 within a VisibilityNetwork 100 but effectively produces a PostgresSQL database thatrepresents the tag, its data and reads over last human legible, commaseparated, date time-stamped record of every tag transaction. Itprovides a total RuBee network history of critical evens includingsignal, errors, rereads, CRC checks and can be used for audits or fornetwork statistics. Sidewinders 302 spool approximately 24 hours of tagdata in a local database, providing protection and backup if any Networkoutages occur over the VPN 303.

FIG. 4 illustrates a block diagram 400 of the RuBee tag 301 a. The RuBeetag 301 a includes a transceiver 406. New long-wavelength (LW under 450Khz) power efficient designs have made it possible to create activetransceivers with IP addresses and peer-to-peer, on-demand,communications, with an acceptable range to work as a local network. TheRuBee tag 301 a also includes a power unit 408. The power unit 408 couldbe a quarter-sized CR2525 Li battery with a 10-year or longer batterylife. The communication is taken place through an antenna 408.

Current RuBee Networks 301 use a protocol known as RuBee IV, and consumeonly a few microamps in standby and less than 1 milliamp in active mode.RuBee tag 301 a may be fully programmable using low cost 4-bitprocessors 403 capable of encryption and decryption and complexfunctions associated with managing IP addresses (DCHP, ARP). RuBee tag301 a is remotely driven form the standby mode to active mode thesidewinder 302.

RuBee Networks 301, offer the advantage of low cost tags and low costbase stations (<$100). Moreover, because RuBee tag 301 a have the powersource 408, they may optionally be equipped with sensors 401, sRAM 404,displays 409, LEDs 402 and may also be low in cost (<$2 per tag). SomeRubee protocol designs also eliminate the battery and cost about 15cents with a reduced range. Networks of thousands of peer-to-peer RuBeetags work reliably as a visibility network. RuBee tags are not affectedby liquids, can be used underwater or as an implantable device, and areminimally affected by steel.

The base station apparatus employed may be that disclosed in U.S.application Ser. No. 11/462,981 filed Aug. 7, 2006, incorporated hereinby reference. The tags employed can be those described in US2007/0115132, published May 24, 2007, incorporated herein by referencefor all purposes. The RF technology can be that described in US2007/0063895, published Mar. 22, 2007, incorporated herein by referencefor all purposes. The tag technology can be that described in U.S. Pat.No. 7,049,963, issued May 23, 2006, incorporated herein by reference forall purposes. The transceiver communicating with the tags can be thatdescribed in US 2007/0120649, published May 31, 2007, incorporatedherein by reference for all purposes.

RuBee industrial visibility networks may be used to provide visibilityon or near steel shelves and in harsh environments such as operatingtheaters (rooms), oil and chemical plants, warehouses and retail stores.Long wavelength, low bandwidth visibility systems and sensor networksare currently in use at industrial installations.

FIG. 5 shows a block diagram 500 of a diagnostic tools used in theDot-Tag Visibility Network 201. The Dot-Tag Visibility Network 201includes a suite of diagnostic tools 501 that run on a laptop. Thediagnostic tools talk direct to the Sidewinder 302 and bypass the Linuxkernel. The tools 501 drive the RuBee base station direct and make itpossible to read and program an individual tag through the RuBee network301. These tools 501 will work from anywhere in the world providing youhave the correct IP address, passwords and VPN authority. They cancollect tag statistics, read memory, change addresses, or almost anyother maintenance diagnostic function as shown in Tables 502 and 503.

The tools 501 produce a data log consistent with Part11 logs andrepresent the supreme check on network and tag integrity.

FIG. 6 shows a block diagram 600 of a Part11 Data Flow. The Sidewinder302 communicates by a VPN 303 to a data server 304 which manages aPostgresSQL database of virtual tags 305. These data links allLinux-Linux and use standard SQL protocols. The Visibility Data Server304 creates and preserves off-site physical backups, as well as Part11human legible records (Archive) 602 of every tag transaction. The Part11records (Archive) 602 include tag signal strength, tag field boundaries,CRC confidence checks, statistics on each tag read, failed reads, packetrelays, noise levels, and tag data.

Part11 data 602 may be encrypted using Tools Data Desk 601 and emailedto a subscriber every hour day or week, and will identify and diagnosetag, antenna or network problems before they happen. Statistics of readsand read errors for individual tags or millions of tags may be routinelyviewed in a few seconds shown in Tables 604, 605 and 606. This data iswritten with an independently verified date time stamp to a WORM opticaldisk drive 603 to create an audit trail that meets 21CFRPart11 for alltag transactions. The Part11 audit trails also meet SEC Rule 17a-4,HIPAA, Sarbanes-Oxleyn (SOX), and DoD 5015.2 standards.

FIG. 7 shows another block diagram 700 of the Part11 Data Flow. TheSidewinder 302 communicates by a VPN 303 to a data server 304 whichmanages a PostgresSQL database of virtual tags 305. These data links allLinux-Linux and use standard SQL protocols. The Visibility Data Server304 creates and preserves the SOX Archive 701. The SOX Archive 701 is ahuman readable comma separated, date time stamped certified record ofevery box or item transaction. It provides a human legible total productnetwork history of critical events including time on shelf, whenremoved, physical inventory, date sold, reorder points, and billinginformation.

SOX data 701 may be encrypted using Tools Data Desk 601 and emailed to asubscriber day, week, or month and will identify and diagnose productinventory delivery problems before they happen. Statistics of productmovement for individual items or millions of items may be routinelyviewed in a few seconds. This data is written with an independentlyverified date time stamp to a WORM optical disk drive 603 to create anaudit trail that meets SEC rules for all product transactions.

FIG. 8 and FIG. 9 shows a block diagram 800 and 900 of a Visibility DataFlow. User Web enabled Visibility Systems/reports and ERP's 806 arecreated by simple plugs to the Visibility Data server 304. The Vis-DataServer 304 contains the full Virtual Tag Database 305 updated by allSidewinders 302. The Tag Database 304 is actively maintained but thesidewinders 302. Standard interfaces are available for PostgresSQL toJAVA, Ruby on Rails, Pentahoe and many other enterprise driven ERPsystems 806. It is possible to create sophisticated and interactivesystems, real-time visibility reports and systems using the Vis-DataServer and plug in in a matter of days.

The Air Traffic Control (ATC) ATC plug 805 is used to control functionswithin a RuBee network 301. For example to turn on a LED 402 on a tagthe tag is accessed using a simple instruction with flash time etcthrough the ATC plug 805. The read times for tags, router start stoptimes, and antenna tune checks etc. are all controlled through the ATCplug 805. The SQL plug 804 is used to support a data requests. Real-timevisibility reports are shown in Table 808.

The user ERP's 806 are also responsible for exports to a customer system809. For example business rules linked to a billing event and allinformation tied to that are exported in Layer 6. The layer 6 includes aUser Event Export Tools 807 that covert a real-time visibility reportsinto report that fits a specific event like billing. Examples of UserEvent Export Tools 807 are Excel, CSV, HL7 and XML-RDF.

FIGS. 10-13 show example of a real life application of the VisibilityNetwork 100. FIG. 10 is a Smart Shelf RuBee Local Net 1000. Typicalsmart shelf application for medical devices. The devices are steel andare packaged in conductive Aluminum as shown in Pictures 1001-1003.Box's are stacked 6-8 high and two to three rows deep.

FIG. 11 is an example 1100 how the Dot-Tag Network 201 works in reallife. The graph 1100 shows signal strength vs time for 24 hours. A fullinventory is carried out each ten minutes for 203 Box's on the shelf.That means each box is checked about 130 times each day. The green dotsrepresent reads, the red represent no-reads on an attempt. Important tonot no miss-reads occur at a high signal. This usually means small burstof noise or that box has been removed.

RuBee Network 301 activated smart shelves 1001 has been placed as anetwork in Hospitals. Orthopedic implants have tags placed on outside ofbox. Note these devices are steel and are packaged with heavy aluminumsealed packages and stacked on steel shelves. The Part11 data 602 andtools shows 24 hours of reads (26,391 per day) and shows that 99.765% or26,329 reads are 100% on first attempt. 0.129 were successful on secondattempt and so on for 100% reads up to five attempts. Local noise, andindividual moving or searching for a box etc. May lead to re-reads asshown in the Table 1102.

FIG. 12 and FIG. 13 how the Dot-Tag Network 201 works when an Orthopedicimplants are removed from the smart shelves 1001 and placed in the cartthat has two levels. Level one 1201 is the inventory pending and leveltwo 1202 inventory used. The Part11 Log 602 provides an archive for alltag and network based transactions. The Sox Log 701 provides an archivefor all product based transactions.

Tables 1301 and 1302 are examples of a real time access to the inventoryof the shelf 1001. It also provided point of use data, usage statistics,and needs predictions.

It will thus be appreciated that the above discussion enables one toprovide a system comprising:

-   -   a plurality of routers, each communicating via an internet with        a server;    -   for each said router, a multiplicity of respective        long-wavelength ID tags each disposed for attachment to an        asset, each said tag comprising a tag antenna operable at a low        radio frequency not exceeding 1 megahertz, a transceiver        operatively connected to said antenna, said transceiver being        operable to transmit and receive data at said low radio        frequency, a programmed data processor to process data received        from the transceiver, said tag having a unique hardware address,        said transceiver emitting an identification signal upon        interrogation by said router;    -   each said router communicating with its respective tags from        time to time via said low radio frequency, said router        maintaining an association between each said tag and a        corresponding IP address;    -   each said router responsive to queries from the server with        information from one or more of its respective tags.

The server can be a user web-based ERP, the server providing real-timevisibility reports. 8. The user web-based ERP may be selected from theset consisting of Eclipse, Pentaho, Ruby on Rails, Google tools, Java,.Net and Weblogic.

At least one of the long-wavelength tags can include a sensor or a LightEmitting Diode (LED).

The server can create and preserve a Part11 human-legible record of tagtransactions. The Part11 human legible records can include tag signalstrength, tag field boundaries, CRC confidence checks, statistics onsaid tag, failed reads, packet relays, noise levels, and the tag data.

The server can create and preserve a Sarbanes-Oxley (SOX) archive, saidSOX archive providing a human-legible total asset network history ofcritical events including time off shelf, when removed, physicalinventory, date sold, reorder thresholds, and billing information.

The system can further comprise a tool for data export from the server,said tool selected from the set consisting of Excel, CSV, HL7 andXML-RDF.

The IP address of a tag may be stored within the tag, for example in anonvolatile memory. In such a case, the router learns the IP address byinterrogating the tag.

On the other hand, the tag may simply have a unique hardware address,and the assignment of an IP address to the tag can take place in therouter (the sidewinder). In such a case, router maintains within therouter a correspondence between the assigned IP address and the hardwareaddress of the tag.

The router may power the tag by bathing the tag in an RF energy field.

It should be noted that the matter contained in the above description orshown in the accompanying drawings should be interpreted as illustrativeand not in a limited sense. The following claims are intended to coverall generic and specific features described herein, as well as allstatements of the scope of the present method and system, which, as amatter of language, might be said to fall there between.

1. A system comprising: a plurality of routers, each communicating viaan internet with a server; for each said router, a multiplicity ofrespective long-wavelength ID tags each disposed for attachment to anasset, each said tag comprising a tag antenna operable at a low radiofrequency not exceeding 1 megahertz, a transceiver operatively connectedto said antenna, said transceiver being operable to transmit and receivedata at said low radio frequency, a programmed data processor to processdata received from the transceiver, said tag having a unique hardwareaddress, said transceiver emitting an identification signal uponinterrogation by said router; each said router communicating with itsrespective tags from time to time via said low radio frequency, saidrouter maintaining an association between each said tag and acorresponding IP address; each said router responsive to queries fromthe server with information from one or more of its respective tags. 2.The system of claim 1 wherein the server is a user web based ERP, andwherein the server provides real-time visibility reports.
 3. The systemof claim 1, wherein at least one of said long-wavelength tags includes asensor.
 4. The system of claim 1, wherein at least one of saidlong-wavelength tags includes a Light Emitting Diode (LED).
 5. Thesystem of claim 1, wherein said server creates and preserves a Part11human-legible record of tag transactions.
 6. The system of claim 5,wherein the Part11 human legible records include tag signal strength,tag field boundaries, CRC confidence checks, statistics on said tag,failed reads, packet relays, noise levels, and the tag data.
 7. Thesystem of claim 1, wherein said server creates and preserves aSarbanes-Oxley (SOX) archive, said SOX archive provides a human legibletotal asset network history of critical events including time off shelf,when removed, physical inventory, date sold, reorder thresholds, andbilling information.
 8. The system of claim 2, wherein the user webbased ERP is selected from the set consisting of Eclipse, Pentaho, Rubyon Rails, Google tools, Java, .Net and Weblogic.
 9. The system of claim1, further comprising a tool for data export from the server, said toolis selected from the set consisting of Excel, CSV, HL7 and XML-RDF. 10.The system of claim 1 wherein for at least one router and for at leastone tag, the tag has its respective IP address stored therewithin, andwherein the router learns the IP address of the at least one tag byinterrogating said tag.
 11. The system of claim 1 wherein for at leastone router and for at least one tag, the router assigns the IP addressto the at least one tag, and the router maintains within the router acorrespondence between the assigned IP address and the hardware addressof the tag.
 12. The system of claim 1 wherein for at least one routerand for at least one tag, the at least one router powers the at leastone tag by bathing the tag in an RF energy field.
 13. A method for usewith a system comprising a plurality of routers, each communicating viaan internet with a server; for each said router, a multiplicity ofrespective long-wavelength ID tags each disposed for attachment to anasset, each said tag comprising a tag antenna operable at a low radiofrequency not exceeding 1 megahertz, a transceiver operatively connectedto said antenna, said transceiver being operable to transmit and receivedata at said low radio frequency, a programmed data processor to processdata received from the transceiver, said tag having a unique hardwareaddress, said transceiver emitting an identification signal uponinterrogation by said router; the method comprising the steps of: foreach router, communicating with its respective tags from time to timevia said low radio frequency, said router maintaining an associationbetween each said tag and a corresponding IP address; for each router,responding to queries from the server with information from one or moreof its respective tags.
 14. The method of claim 13 wherein for at leastone router and for at least one tag, the tag has its respective IPaddress stored therewithin, the method further comprising the step of:at the at least one router, interrogating the at least one tag, therebylearning the IP address of the at least one tag.
 15. The method of claim13 wherein for at least one router and for at least one tag, the atleast one tag does not have an IP address stored therewithin, the methodfurther comprising the step of: at the at least one router, assigningthe IP address to the at least one tag, and at the at least one router,maintaining within the router a correspondence between the assigned IPaddress and the hardware address of the tag.
 16. The method of claim 13wherein for at least one router and for at least one tag, the methodfurther comprises the step of: at the at least one router, powering theat least one tag by bathing the tag in an RF energy field.
 17. A router,the router disposed for communication via an internet with a server; therouter comprising means for communication with a multiplicity ofrespective long-wavelength ID tags each disposed for attachment to anasset, each said tag comprising a tag antenna operable at a low radiofrequency not exceeding 1 megahertz, a transceiver operatively connectedto said antenna, said transceiver being operable to transmit and receivedata at said low radio frequency, a programmed data processor to processdata received from the transceiver, said tag having a unique hardwareaddress, said transceiver emitting an identification signal uponinterrogation by said router; the router disposed to communicate withits respective tags from time to time via said low radio frequency, saidrouter maintaining an association between each said tag and acorresponding IP address; each said router responsive to queries fromthe server with information from one or more of its respective tags. 18.The system of claim 17 wherein for at least one tag, the tag has itsrespective IP address stored therewithin, and wherein the router learnsthe IP address of the at least one tag by interrogating said tag. 19.The system of claim 17 wherein for at least one tag, the router assignsthe IP address to the at least one tag, and the router maintains withinthe router a correspondence between the assigned IP address and thehardware address of the tag.
 20. The system of claim 17 wherein for atleast one tag, the router powers the at least one tag by bathing the tagin an RF energy field.